Tk_Window _s_l_a_v_e (in) Window whose geometry is to be controlled.
Tk_Window _m_a_s_t_e_r (in) Window relative to which _s_l_a_v_e's geometry
will be controlled.
int _x (in) Desired x-coordinate of _s_l_a_v_e in _m_a_s_t_e_r,
measured in pixels from the inside of
_m_a_s_t_e_r's left border to the outside of
_s_l_a_v_e's left border.
int _y (in) Desired y-coordinate of _s_l_a_v_e in _m_a_s_t_e_r,
measured in pixels from the inside of
_m_a_s_t_e_r's top border to the outside of
_s_l_a_v_e's top border.
int _w_i_d_t_h (in) Desired width for _s_l_a_v_e, in pixels.
int _h_e_i_g_h_t (in) Desired height for _s_l_a_v_e, in pixels.
DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
TTTTkkkk____MMMMaaaaiiiinnnnttttaaaaiiiinnnnGGGGeeeeoooommmmeeeettttrrrryyyy and TTTTkkkk____UUUUnnnnmmmmaaaaiiiinnnnttttaaaaiiiinnnnGGGGeeeeoooommmmeeeettttrrrryyyy make it easier for geometry
managers to deal with slaves whose masters are not their parents. Three
problems arise if the master for a slave is not its parent:
(a) The x- and y-position of the slave must be translated from the
coordinate system of the master to that of the parent before
positioning the slave.
(b) If the master window, or any of its ancestors up to the slave's
parent, is moved, then the slave must be repositioned within its
parent in order to maintain the correct position relative to the
master.
(c) If the master or one of its ancestors is mapped or unmapped, then
the slave must be mapped or unmapped to correspond.
None of these problems is an issue if the parent and master are the same.
For example, if the master or one of its ancestors is unmapped, the slave
TTTTkkkk____MMMMaaaaiiiinnnnttttaaaaiiiinnnnGGGGeeeeoooommmmeeeettttrrrryyyy deals with these problems for slaves whose masters
aren't their parents. TTTTkkkk____MMMMaaaaiiiinnnnttttaaaaiiiinnnnGGGGeeeeoooommmmeeeettttrrrryyyy is typically called by a
window manager once it has decided where a slave should be positioned
relative to its master. TTTTkkkk____MMMMaaaaiiiinnnnttttaaaaiiiinnnnGGGGeeeeoooommmmeeeettttrrrryyyy translates the coordinates
to the coordinate system of _s_l_a_v_e's parent and then moves and resizes the
slave appropriately. Furthermore, it remembers the desired position and
creates event handlers to monitor the master and all of its ancestors up
to (but not including) the slave's parent. If any of these windows is
moved, mapped, or unmapped, the slave will be adjusted so that it is
mapped only when the master is mapped and its geometry relative to the
master remains as specified by _x, _y, _w_i_d_t_h, and _h_e_i_g_h_t.
When a window manager relinquishes control over a window, or if it
decides that it does not want the window to appear on the screen under
any conditions, it calls TTTTkkkk____UUUUnnnnmmmmaaaaiiiinnnnttttaaaaiiiinnnnGGGGeeeeoooommmmeeeettttrrrryyyy. TTTTkkkk____UUUUnnnnmmmmaaaaiiiinnnnttttaaaaiiiinnnnGGGGeeeeoooommmmeeeettttrrrryyyy
unmaps the window and cancels any previous calls to TTTTkkkk____MMMMaaaaiiiinnnnttttaaaaiiiinnnnGGGGeeeeoooommmmeeeettttrrrryyyy
for the _m_a_s_t_e_r-_s_l_a_v_e pair, so that the slave's geometry and mapped state
are no longer maintained automatically. TTTTkkkk____UUUUnnnnmmmmaaaaiiiinnnnttttaaaaiiiinnnnGGGGeeeeoooommmmeeeettttrrrryyyy need not
be called by a geometry manager if the slave, the master, or any of the
master's ancestors is destroyed: Tk will call it automatically.
If TTTTkkkk____MMMMaaaaiiiinnnnttttaaaaiiiinnnnGGGGeeeeoooommmmeeeettttrrrryyyy is called repeatedly for the same _m_a_s_t_e_r-_s_l_a_v_e
pair, the information from the most recent call supersedes any older
information. If TTTTkkkk____UUUUnnnnmmmmaaaaiiiinnnnttttaaaaiiiinnnnGGGGeeeeoooommmmeeeettttrrrryyyy is called for a _m_a_s_t_e_r-_s_l_a_v_e pair
that is isn't currently managed, the call has no effect.